Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Added remote control commands for IQ recording #1405

Closed
wants to merge 6 commits into from

Conversation

mhassell
Copy link

I expanded the remote control / telnet commands to include AOIQ and LOIQ to emulate the AOS and LOS commands to capture the IQ data instead of audio. I connected the remote control commands to the IQ tool by making a public pointer in remote control point to the IQ tool.

I tested my changes by opening two shells and launching gqrx from the first shell and enabled TCP communications. On the second shell, I then ran telnet and sent the AOIQ and LOIQ commands to GQRX, confirming RPRT 0 responses:

telnet 127.0.0.1 7356

Trying 127.0.0.1...

Connected to 127.0.0.1.

Escape character is '^]'.

AOIQ

RPRT 0

LOIQ

RPRT 0

I then checked that a .raw file was created where specified in the gqrx configuration, and that was indeed a collection of IQ data I was able to play back in GQRX to show functionality.

@mhassell
Copy link
Author

I should add this partially implements this requested feature

@argilo
Copy link
Member

argilo commented Feb 4, 2025

By the way, there is a previous pull request implementing the same feature (but using different commands): #1142

Perhaps we should revive that pull request instead?

@argilo argilo added the feature label Feb 4, 2025
@mhassell
Copy link
Author

mhassell commented Feb 4, 2025

I will work on that branch then -- may I ask the preferred procedure? Just branch off of that branch, merge master, test and open another PR?

@vladisslav2011
Copy link
Contributor

vladisslav2011 commented Feb 5, 2025

may I ask the preferred procedure?

  1. Sync your fork (master branch)
  2. Pull the updated master locally
git checkout master
git pull
  1. Rebase your branch on top of the master branch
git checkout mh-feat1403-iq-recording
git rebase master

In case of conflict, fix the code, add changed files and

git rebase --continue
  1. Force-push your branch back to github
git push --force

This should result in a clean history without "Merge master into..." useless commits.

@argilo
Copy link
Member

argilo commented Feb 5, 2025

I rebased #1142 and pushed the changes (since I have permission as the project maintainer). My suggestion would be to try out that branch and leave your feedback on that PR.

@argilo
Copy link
Member

argilo commented Feb 7, 2025

Closing in favour of #1142.

@argilo argilo closed this Feb 7, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants